@AnnaMalekITIntegro please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="IT.integro sp. z o.o."

Hi @AnnaMalekITIntegro,

I'd love to get these changes in in time for 2025 wave 1, but I would need some tests in order to process this PR. Do you happen to have some tests you can add, which verify that your changes work as intended?

Hi @AnnaMalekITIntegro,

I'd love to get these changes in in time for 2025 wave 1, but I would need some tests in order to process this PR. Do you happen to have some tests you can add, which verify that your changes work as intended?

Hi,
I'll add tests to the end of this week.

Hi @JesperSchulz
Please let me know if this is enough :)

Alright! Let's do this one! Only challenge: as we already have that feature in CZ, we need to delocalize, which will take some more time than usual. But we'll get there!

@AnnaMalekITIntegro, @VolodySyn has merged your idea with the code we had in CZ version to make de-localization easier. You will find that the code is slightly different from what you suggested, but it should fully support the scenario you were looking for!

I will merge this code (if it compiles) and then we'll update it once the internal PR has been processed. The feature is set to release with 26.0 in April!

@JesperSchulz please let me know if I should do anything in this PR. :)

@JesperSchulz please let me know if I should do anything in this PR. :)

There is no action on you. The feature has been added. I will close this PR, as your requested changes should have been addressed 😊